Small data communications in a wireless communication network

ABSTRACT

Technology for performing small data transmissions at a user equipment (UE) is disclosed. An apparatus of the UE can receive, from an eNodeB, a small data transmission indicator that instructs the UE to establish a fast radio resource control (RRC) connection with the eNodeB. The apparatus of the UE can initiate a random access channel (RACH) procedure in order to establish the fast RRC connection with the eNodeB. The fast RRC connection may not include the establishment of bearers between the UE and the eNodeB. The apparatus of the UE can perform a small data transmission with the eNodeB using the fast RRC connection between the UE and the eNodeB.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/734,371, which has matured into U.S. Pat. No. 9,107,103, filed Jan.4, 2013, which claims the benefit under 35 U.S.C. §119(e) of a U.S.Provisional Patent Application filed Apr. 13, 2012 in the U.S. Patentand Trademark Office and assigned Ser. No. 61/624,185, both of which arehereby incorporated by reference in their entirety

BACKGROUND

In general, machine-to-machine (M2M) communication or Machine TypeCommunication (MTC) may refer to technologies that allow wireless andwired systems to communicate with other devices without any humanintervention. M2M communication may use a device such as, for example, asensor or meter to collect information. The M2M device can communicatevia a mobile network (e.g., wireless, wired, hybrid) with an MTCapplication server (e.g., software program) that can use or request datafrom the M2M device.

The expansion of mobile networks (e.g., broadband wireless accessnetworks, wide area networks) across the world, along with the increasedspeed/bandwidth and reduced power of wireless communication, hasfacilitated the growth of M2M communication. Although the amount of datasent by M2M devices is very small, a large number of these devicesconnected to a wireless network and used concurrently may increase adata load and overhead expense on a network. Therefore, currenttechniques for transmitting small data payloads (e.g., machine typecommunication data) may be inefficient or incompatible with emergingmobile networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the invention will be apparent from thedetailed description which follows, taken in conjunction with theaccompanying drawings, which together illustrate, by way of example,features of the invention; and, wherein:

FIG. 1 schematically illustrates an example scheme for performing smalldata transmissions in accordance with an example.

FIG. 2 schematically illustrates another example scheme for performingsmall data transmissions in accordance with an example.

FIG. 3 schematically illustrates an example scheme for transmittingmulticast information transfer messages in accordance with an example.

FIG. 4 schematically illustrates another example scheme for transmittingmulticast information transfer messages in accordance with an example.

FIG. 5 is a table showing example values associated with multicastinformation transfer messages in accordance with an example.

FIG. 6 depicts a flow chart of a method for enabling small datatransmissions in a user equipment configured for machine typecommunication in accordance with an embodiment of the present invention.

FIG. 7 illustrates a block diagram of a user equipment in accordancewith an example.

FIG. 8 illustrates a mobile wireless device in accordance with anexample.

Reference will now be made to the exemplary embodiments illustrated, andspecific language will be used herein to describe the same. It willnevertheless be understood that no limitation of the scope of theinvention is thereby intended.

DETAILED DESCRIPTION

Before the present invention is disclosed and described, it is to beunderstood that this invention is not limited to the particularstructures, process steps, or materials disclosed herein, but isextended to equivalents thereof as would be recognized by thoseordinarily skilled in the relevant arts. It should also be understoodthat terminology employed herein is used for the purpose of describingparticular embodiments only and is not intended to be limiting.

Definitions

As used herein, the term “substantially” refers to the complete ornearly complete extent or degree of an action, characteristic, property,state, structure, item, or result. For example, an object that is“substantially” enclosed would mean that the object is either completelyenclosed or nearly completely enclosed. The exact allowable degree ofdeviation from absolute completeness may in some cases depend on thespecific context. However, generally speaking the nearness of completionwill be so as to have the same overall result as if absolute and totalcompletion were obtained. The use of “substantially” is equallyapplicable when used in a negative connotation to refer to the completeor near complete lack of an action, characteristic, property, state,structure, item, or result.

Other terms may be defined elsewhere in the body of this specification.

Example Embodiments

An initial overview of technology embodiments is provided below and thenspecific technology embodiments are described in further detail later.This initial summary is intended to aid readers in understanding thetechnology more quickly but is not intended to identify key features oressential features of the technology nor is it intended to limit thescope of the claimed subject matter.

With a wide range of potential applications, Machine Type Communication(MTC) or Machine to Machine (M2M) communication has gained largeinterest among equipment vendors, mobile network operators, and MTCspecialist companies. As used herein, the terms M2M and MTC are usedsynonymously. MTC is a form of data communication among one or moreentities that does not necessarily need human interaction. Generally, anMTC device can be a user equipment (UE) equipped for MTC. The UE cancommunicate through a Public Land Mobile Network (PLMN) with MTC serversand/or other MTC devices. In addition, the MTC device can communicatelocally (e.g., wirelessly, through a personal area network (PAN), orhardwired) with other entities that provide the MTC device with data(e.g., a small data payload). Thereafter, the MTC device can process thedata and then transmit the data to the MTC servers and/or other MTCdevices. The MTC devices can include health monitoring devices, smartmeters, sensors, etc.

The MTC server can communicate to the PLMN, as well as to the MTCdevices (e.g., UEs configured for MTC) through the PLMN. In addition,the MTC server can be further configured to communicate with anInterworking Function (IWF) to trigger a transmission of a small datapayload from the server to the MTC device.

MTC devices can transmit (i.e., send or receive) small amounts of dataover a network. The small amount of data typically ranges from a fewbits to kilobits of data. The network can be a wireless wide areanetwork (WWAN) or wireless local area network (WLAN) based on a selectedradio access network (RAN) technology. The WWAN can be configured tooperate based on a cellular networking standard such as IEEE 802.16standard, commonly referred to as WiMAX (worldwide interoperability formicrowave access), and the third generation partnership project (3GPP).Releases of the IEEE 802.16 standard include the IEEE 802.16e-2005,802.16-2009, and 802.16m-2011. Releases of the 3GPP standard include the3GPP LTE, Release 8 in the fourth quarter of 2008, 3GPP LTE AdvancedRelease 10 in the first quarter of 2011, and 3GPP LTE Release 11 in thethird quarter of 2012.

Standards such as WiFi or Bluetooth are used to provide wireless localarea networks (WLAN). WiFi is a common name provided to an Institute ofElectronics and Electrical Engineers (IEEE) 802.11 set of standards forcommunicating in unlicensed spectrum including the 2.4, 3.7 and 5 GHzfrequency bands. The set of standards includes the IEEE 802.11a standardreleased in 1999 for communication in the 5 GHz and 3.7 GHz band, theIEEE 802.11b standard, also released in 1999 for communication in the2.4 GHz band, the 802.11g standard released in 2003 for communication inthe 2.4 GHz range via orthogonal frequency division multiplexing (OFDM)and/or direct sequence spread spectrum (DSSS), and the 802.11n standardreleased in 2009 for communication in the 2.4 GHz and 5 GHz bands usingmultiple-input multiple-output (MIMO).

In some examples, the MTC device can transmit the small data (e.g.,measurements, temperature) via a WWAN or WLAN network in response to arequest from an MTC server to send the small data. For example, the MTCserver can communicate via an evolved packet core (EPC) of a 3GPP LTEnetwork with a RAN having an eNB that can transmit a request for thedata from the UE. In response to the request, the MTC device can wake upfrom an idle mode and send the small data. In another example, the MTCdevice can periodically wake up from an idle mode and send small data(e.g., measurements) to the server via the eNB. Generally, the smalldata is transmitted as a short data transfer in a single packet orburst. To reduce the overhead used to allow an MTC device to connectwith a WWAN and transmit the small data, an indicator can be used toallow the wireless network to be aware that a small data transmissionwill occur. The indicator can be used by the wireless network to reducethe amount of overhead needed to connect to the network in order tocommunicate the small data transmission.

In one embodiment, the small data transmissions can have a minimalimpact on the network by reducing signaling overhead, network resources,and/or delay for reallocation. In addition, the MTC device can beattached (e.g., by an established Radio Resource Control (RRC)connection) or detached to/from the network before transmission of thesmall data payload (e.g., when the small data payload transmission istriggered). In some embodiments, the UE can be connected with the eNB inan RRC connected mode or an idle mode when the small data payloadtransmission is triggered. The small data payload can be defined and/orconfigured per subscription or by a network operator policy. In someembodiments, the observed size of the instances of data exchange can beon the order of 1K (1024) octets. However, other sizes of data exchangeare also possible, as can be appreciated.

The MTC device (or a UE supporting MTC applications) may transmit thesmall data in a downlink (i.e., from the eNB to the UE) or in an uplink(i.e., from the UE to the eNB). A downlink small data transmission caninclude a small data transmission indicator bit, along with anacknowledgement on the uplink. The acknowledgement can be a signaltransmitted to indicate that one or more blocks of data have beensuccessfully received and decoded. In some examples, the acknowledgementis not sent in response to the downlink small data transmission. Thedownlink small data transmission can include a small data commandrequest to pull the data from the UE. In addition, an uplink small datatransmission can include a small data transmission indicator bit, and anacknowledgement can be included on the downlink. The uplink small datatransmission can occur after receiving a command request from the eNB.

The MTC applications that are executed on the MTC devices can be relatedto a variety of areas, such as security (e.g., surveillance systems,driver security), tracking and tracing (e.g., asset tracking,navigation, traffic information, road tolling), payment (e.g., vendingmachines, gaming machines), health (e.g., monitoring vital signs,supporting the elderly or handicapped), remote maintenance/control(e.g., sensors, lighting, vehicle diagnostics), metering (e.g., power,gas, water, heating), and/or consumer devices (e.g., digital cameras).

FIG. 1 schematically illustrates an example scheme for performing smalldata transmissions in accordance with an example. An evolved node (eNB)can transmit a system information block (SIB), such as a SIB type 1 tothe user equipment (UE). In some examples, the UE can include or becommunicatively coupled with smart meters or sensors to collect smallamounts of information for transmission (e.g., health monitoringdevices, vending machines, and the like configured to collectinformation about temperature, inventory, etc.).

In general, the SIB can include system information that is to bebroadcasted to the UE. The SIB can include a set of functionally-relatedparameters. For example, in Third Generation Partnership Project LongTerm Evolution (3GPP LTE), the SIB can include a limited number of themost frequently transmitted parameters that are used by the UE to accessa network. According to various embodiments of the present invention,the SIB can include system information related to small datatransmissions for MTC. As will be discussed in further detail below, theUE generally needs to wake up from an idle mode in order to receive theSIB containing the system information.

In general, the SIB can include system information and/or configurationparameters that are specific to UEs that are configured for MTC. Inaddition, the SIB can include Extended Access Barring (EAB) informationand/or Access Class Barring (ACB) information. The EAB information canbe used to control Mobile Originating access attempts from UEs that areconfigured for EAB, in order to prevent an overload of the accessnetwork and/or the core network. In a congestion situation, an operatorcan restrict access from UEs that are configured for EAB, whilepermitting access to other UEs. The ACB information functions torestrict UE access attempts when the UE is not a member of at least oneAccess Class corresponding to permitted classes that are signaled overan air interface.

In one embodiment, a SIB type 1 (SIB1) can be used to communicate thesmall data transmission indicator bit. The SIB type 1 typically containsinformation relevant when evaluating if a UE is allowed to access a cellin a RAN. Also, the SIB1 can supply the UE with the scheduling of othersystem information.

After receiving the SIB from the eNB, the UE can read the systeminformation included in the SIB. In some examples, the SIB can indicateupdated system information in a different SIB (e.g., SIBx). The SIBx caninclude information relating to system parameters associated with smalldata transmissions for MTC devices. In other words, the UE can receive aSIB from the eNB, and the SIB can include a pointer to the SIBx.Thereafter, the UE can read the SIBx in order to read the updated systeminformation.

In some embodiments of the present invention, the UE can read a smalldata transmission indicator in the system information included in theSIB. The small data transmission indicator can notify the UE that theeNB desires to transmit a small amount of data. In some examples, the UEcan read a small data transmission command request in the systeminformation. The small data transmission command request can notify theUE that the eNB is asking the UE to transmit a small data payload (e.g.,measurement data, reporting data).

In addition, the UE can read a small data payload included in the systeminformation block. The small data payload can include informationassociated with MTC applications involving security, health, metering,etc. In addition, the small data payload can include information, suchas sensor or meter measurement, inventory level, etc. The data payload(e.g., MTC data payload) can be smaller than a preconfigured thresholdto define a small data payload in some embodiments. In some embodiments,the preconfigured threshold can be set by a subscription or a networkoperator policy.

After reading the SIB, the UE can perform the small data transmissionwith the eNB, based on the system information included in the SIB, suchas the SIB1. For example, the UE can read a small data transmissionindicator in the system information, and then subsequently perform thesmall data transmission with the eNB. In some embodiments, the UE canperform the small data transmission by establishing a radio resourcecontrol (RRC) connection with the eNB. In general, the RRC protocolcovers the broadcasting of system information. The RRC protocol handlesthe Layer 3 control plane signaling by which the evolved universalterrestrial radio access network (E-UTRAN) controls the behaviorsassociated with the UE. The E-UTRAN consists of eNBs and provides theE-UTRAN user plane and control plane (RRC) protocol terminations towardsthe UE. Alternatively, the UE can perform the small data transmission byexecuting a “fast” RRC connection with the eNB. As will be discussed ingreater detail below, the “fast” RRC connection can involve fewer stepsas compared to a typical RRC connection.

In one embodiment, when establishing an RRC connection, the UE caninitiate the RRC connection while in RRC_IDLE mode. In other words, theUE can transition from RRC_IDLE mode to RRC_CONNECTED mode. The UE cansend a RRCConnectionRequest message to the E-UTRAN. In response, theE-UTRAN can send an RRCConnectionSetup message to the UE. Upon the UEsending an RRCConnectionSetupComplete message to the E-UTRAN, the RRCconnection is successfully established. If the RRC connection is notsuccessfully established, then the E-UTRAN can send anRRCConnectionReject message in response to the RRCConnectionRequestmessage sent by the UE.

In addition, an RRC connection reconfiguration procedure can be used tomodify the RRC connection. The RRC connection can be modified toestablish, modify, and/or release radio bearers. The E-UTRAN (e.g., theeNB) can initiate the RRC connection reconfiguration procedure to a UEduring an RRC_CONNECTED mode. The eNB can send anRRCConnectionReconfiguration message to the UE In response, the UE cansend an RRCConnectionReconfigurationComplete message to the eNB therebysuccessfully reconfiguring the RRC connection. In general, one or moreeNBs can be included in the E-UTRAN, but the UE may be connected to oneeNB at any given time. If the RRC connection reconfiguration is notsuccessfully established, then the UE and/or the eNB may begin an RRCconnection re-establishment procedure.

In contrast to the RRC connection, the “fast” RRC connection may referto an RRC connection that is executed between the UE and the E-UTRANuntil the RRCConnectionSetupComplete phase. As previously discussed,upon the UE sending the RRCConnectionSetupComplete message to theE-UTRAN, the RRC connection is successfully established. A “fast” RRCconnection does not include the messages exchanged related to bearerestablishment between the UE and the E-UTRAN during the RRC ConnectionReconfiguration. Generally, bearers can be described as an end-to-endtunnel or pipeline. The bearers are generally established when acontinuous data stream is to be transmitted (e.g., starting a webpagedownload or a call). In addition, bearers can be established when thedata has a larger size as compared to the small data. Therefore, whenperforming short data transfers (e.g., small data transmissions), it maybe unnecessary to establish the bearers. Accordingly, a “fast” RRCconnection can be used to more quickly form a connection between a UEand an eNB to communicate a small data transmission. Once the “fast” RRCconnection is executed, the UE can indicate a desire to go into anRRC_IDLE mode.

In addition, the UE can perform or attempt a random access channel(RACH) communication in order to execute a “fast” RRC connection betweenthe UE and the eNB. In general, RACH is a communication mechanism usedby a UE to communicate with an eNB in order to initially synchronize theUE's transmission with the eNB. Additionally, RACH is a transportchannel that can be used for access to the network when the UE does nothave accurate uplink timing synchronization, or when the UE does nothave an allocated uplink transmission resource. Therefore, after readingan indication of small data on downlink, the UE can initiate and performRACH to enter the RRC_CONNECTED mode. Similarly, the UE can initiate andperform RACH to enter the RRC_CONNECTED mode after the UE reads acommand request for new data to be sent on an uplink. Subsequent to theUE performing RACH, the UE can execute the “fast” RRC connection inorder to perform the small data transmission.

In some embodiments, the UE can perform the small data transmission byexecuting a “fast” RRC connection with the eNB, in response to readingthe small data transmission indicator (included in the SIB) receivedfrom the eNB. In some examples, the UE can perform the small datatransmission by sending uplink measurement data or report data to theeNB, in response to reading the small data transmission request(included in the SIB) received from the eNB.

In addition, the UE can read a small data payload included in the SIB.The small data payload can be defined according to a subscription and/ora network operator policy. In addition, the small data payload caninclude small data relating to an application operating on the UE, suchas a traffic congestion application, an energy wastage application, ahome monitoring application, a parking guidance application, anelectronic meter reading application, or another MTC type communication.In addition, the small data can be associated with applications relatedto a variety of different areas, such as security, health, metering,etc. In some cases, the UE can read the small data itself from the SIB,and does not establish either a “fast” RRC connection or a RRCconnection, as the UE is not sending data on an uplink.

In some examples, the SIB can be received, by the UE from the eNB, basedon a paging notification (or a paging message). The paging notificationcan include a small data transmission to indicate a pointer to updatesin the SIB (e.g., a pointer to a new SIB1x). For example, the eNB cansend a paging notification to the UE, indicating that the SIB includessystem information related to small data transmissions to the MTC device(or the UE configured for MTC). The paging notification is received bythe UE according to a paging cycle (or an equivalent cycle period) ofthe UE. In general, paging is a mechanism in which the eNB notifies theUE (which is in idle mode) of downlink data or a broadcast message to besent to the UE. After the UE is woken up from idle mode and reads thecontents of the paging message to learn of the updated systeminformation, the UE can then initiate the appropriate procedures forreceiving the SIB from the eNB. Since the paging mechanism generallyoccurs when the UE is in idle mode, the UE can monitor, in idle mode,whether the network is attempting to send any paging messages to the UE.During the idle mode, the UE may wake up to read the SIB based on apaging interval. In some examples, the SIB may be sent periodically tothe UE. However, the paging mechanism may also occur during a connectedmode of the UE. Thus, the SIB may be periodically sent to the UE, andthen subsequently read by the UE, while in both idle mode and connectedmode. In general, a paging message is a downlink broadcasted messagethat may notify UEs of an incoming call/data and/or a change in thesystem information (SI). The paging message can be sent subject to apaging cycle which defines how often (e.g., a default period or amodified period) the UE searches for a new paging message from the eNB.

In some examples, subsequent to the UE waking up from idle mode andreading the paging message from the eNB, the UE can determine anidentifier of the paging message. If the identifier of the pagingmessage matches an identifier of the UE, then the UE can proceed toestablish an RRC connection with the eNB in order to receive thedownlink data or broadcasted message from the eNB.

FIG. 2 schematically illustrates an example scheme for performing smalldata transmissions in accordance with an example. For instance, a UEconfigured for MTC can receive a multicast information transfer messagefrom an eNB. In other words, the multicast information transfer messagecan be used to convey information related to small data transmissions.In addition, the multicast information transfer message can be used totransmit MTC-related notifications (e.g., data pertaining to MTCactivities, such as an energy wastage warning in a smart grid, upcomingtraffic congestion in an MTC application related to road sideassistance).

The multicast information transfer message can notify the UE of updatedsystem information in a SIB relating to the small data transmission. Themulticast information transfer message can include the new SIB receivedby the UE. In some examples, the multicast information transfer messagecan include a pointer to a new SIB (e.g., SIB1x) containing updatedsystem information. Thereafter, the UE can read the SIB1x, and based onthe parameters contained in the SIBx, perform the small datatransmission.

In some embodiments of the present invention, the multicast informationtransfer message can be received by the UE during an RRC idle mode.Furthermore, the multicast information transfer message can be receivedin a paging cycle of the UE during the RRC idle mode. In other words,the multicast information transfer message may page the UE while in idlemode. The paging cycle can be a Default Paging Cycle, or the pagingcycle can be new cycles that are defined specifically for delay tolerantdevices and/or MTC devices or MTC applications. The Default Paging Cyclecan include values of 32, 64, 128, and 256 radio frames can be used. Theradio frames can each be 10 milliseconds (ms) in length. The number ofradio frames can be further increased for MTC devices (e.g., 1024 radioframes) depending on the frequency of the multicast transfer informationmessages sent by the eNB. Thus, multicast information transfer messagesthat are transmitted with low frequency may result in a higher number ofradio frames. Based on the paging cycle (either an existing paging cycleor a new paging cycle developed specifically for delay tolerantdevices), the UE can periodically search for paging messages receivedfrom the eNB.

In some examples, the multicast information transfer message can includea small data payload, as well as an updated SIB including a small datatransmission indicator and/or a small data command request.

In some embodiments of the present invention, the UE can read theupdated system information in the SIB when notified of the change to theSIB by the multicast information transfer message from the eNB, whereinthe updated system information in the SIB relates to small datatransmissions communicated by the UE. For example, the UE can read asmall data transmission indicator in the updated system information,wherein the updated system information is received by the UE in themulticast information transfer message. In addition, the UE can read asmall data transmission command request in the updated systeminformation, wherein the updated system information is received by theUE in the multicast information transfer message. Furthermore, the UEcan read a small data payload in the multicast information transfermessage.

In some examples, the UE can communicate the small data transmission tothe eNB, based on the updated system information included as part of themulticast information transfer message. If the SIB includes a small dataindicator, then the UE can receive the small data on downlink. Incontrast, if the SIB includes a small data request, then the UE can sendthe small data on uplink. In some examples, the UE can perform the smalldata transmission by establishing an RRC connection, with the eNB, inresponse to the small data transmission indicator received in themulticast information transfer message. Alternatively, the UE canperform the small data transmission by executing a “fast” RRCconnection, as previously discussed. In addition, the UE can perform thesmall data transmission by sending uplink measurement data, to the eNB,in response to the small data transmission command request received aspart of the multicast information transfer message.

In some examples, the UE can monitor a Physical Downlink Control Channel(PDCCH) during the RRC idle mode of the UE in order to identify a pagingmessage that indicates a new multicast information transfer message. Ingeneral, the PDCCH is a downlink control channel used to transfercontrol information to mobile devices (e.g., MTC devices). The PDCCH candefine the configurations of the paging channel and the shared downlinkchannels. In addition, the PDCCH can define the uplink transmissionscheduling information in order to coordinate access control to a radiosystem. In addition, the UE can monitor the PDCCH channel at regularintervals based on discontinuous reception (DRX) parameters that aresuitable for delay tolerant UEs. In other words, the DRX parameters candetermine the periods when the UE is to wake up from the idle mode, andthen check for paging messages received from the eNB. In some examples,the UE can monitor the PDCCH channel at regular intervals based onparameters other than DRX parameters.

FIG. 3 schematically illustrates an example scheme for transmittingmulticast information transfer messages in accordance with an example.For example, an eNB can contain circuitry to receive a multicastinformation transfer message from a Mobility management Entity (MME). Ingeneral, the MME is the control node that processes the signalingbetween the UE and the Core Network (CN). In addition, the MME supportsfunctions related to bearer and connection management. The multicastinformation transfer message can be initiated by an MTC server (or otherelement in the network), and then sent to the MME, which subsequentlysends the multicast information transfer message to the eNB. In someexamples, the multicast information transfer message can be initiated bythe MME. As previously discussed, the multicast information transfermessage can include a small data payload, a small data transmissionindicator, or a small data transmission command request. The small datapayload can include data related to an MTC application, such as atraffic congestion application, an energy wastage application, a homemonitoring application, a parking guidance application, an electricmeter reading application, and/or other applications involving smalldata transmission between MTC devices and MTC servers.

In some examples, the eNB can determine a Radio Network TemporaryIdentifier (RNTI) used for transmitting the multicast informationtransfer message to the UE. The RNTI can be used to identify UEs withinan E-UTRAN, and particularly in signaling messages between the UE andthe E-UTRAN. In particular, the eNB can determine a RNTI specificallyrelated to multicast (e.g., MC-RNTI). The MC-RNTI can be a fixed value(e.g., FFFC) or a variable value. The variable value can be derived atthe eNB using an International Mobile Subscriber Identity (IMSI)received from the MME. In general, the IMSI is a unique numberassociated with each UE (e.g., MTC device).

Based on the MC-RNTI, the eNB can transmit the multicast informationtransfer message to the UE. In other words, the eNB can transmit themulticast information transfer message to a UE having a correspondingMC-RNTI. Furthermore, the MME can transmit the multicast informationtransfer message to the eNB using a S1 Application Protocol (S1AP). Inaddition, the eNB can transmit the multicast information transfermessage to the UE using a RRC connection or a “fast” RRC connection.Depending on the information included in the multicast informationtransfer message (e.g., small data payload, small data transmissionindicator, small data transmission command request), either an RRCconnection or a “fast” RRC connection can be used.

In addition, the UE can identify the MC-RNTI by monitoring the PDCCH,based on the DRX parameters or other parameters, for the MC-RNTI values.In other words, if the PDCCH contains the MC-RNTI value, then the UE isnotified of a new multicast information transfer message. The MC-RNTIcan indicate to the UE that the enB is sending the multicast informationtransfer message.

FIG. 4 schematically illustrates another example scheme for transmittingmulticast information transfer messages in accordance with an example.For example, the eNB can transmit a multicast information transfermessage to a specific UE, a single multicast group of UEs, or aplurality of multicast groups of UEs. If the MC-RNTI is fixed, the eNBcan transmit the multicast information transfer message to a singlemulticast group of UEs. In other words, a fixed MC-RNTI has onemulticast group per eNB. For example, an energy wastage application mayuse a fixed MC-RNTI if the eNB only sends multicast information transfermessages to the UEs using that application. In some examples, theMC-RNTI is variable, which enables the eNB to send the multicastinformation transfer message to a plurality of multicast groups of UEs.As previously discussed, the MC-RNTI can be used to identify selectedUEs within an E-UTRAN.

As an example, an eNB can transmit small data to a specific UE based ona health-related MTC application. As another example, the eNB cantransmit a small data transmission command request relating to a homemonitoring application to a single multicast group of UEs. In addition,the eNB can transmit a small data transmission indicator relating to atraffic congestion application to a plurality of multicast groups ofUEs.

As illustrated in FIG. 4, an eNB can transmit a multicast informationtransfer message to a plurality of UEs (e.g., UE₁, UE₂, UE₃, UE₄, UE₅and UE₆). As an example, UE₁ and UE₂ can be included in a singlemulticast group according to MC-RNTI_(A). In addition, UE₄ and UE₅ canbe included in a single multicast group according to MC-RNTI_(B). Insome examples, UE₃ and UE₆ can be specific UEs that receive themulticast information transfer message from the eNB.

FIG. 5 is a table showing example values for multicast informationtransfer messages in accordance with an example. As previouslydiscussed, the multicast information transfer messages can be used forsmall data transmissions. The values may include hexadecimal values thatare fixed (e.g., FFFC). In addition, the values can be variable valuesthat are derived from the IMSI. The RNTIs used specifically to identifymulticast information transfer messages can be referred to as MC-RNTIs.In addition to MC-RNTIs, there can be various other types of RNTIs, suchas Cell-RNTI (C-RNTI), Paging-RNTI (P-RNTI), Random Access-RNTI(RA-RNTI), and System Information-RNTI (SI-RNTI).

The values (both fixed and variable) related to transmitting themulticast information transfer messages can be associated with a pagingchannel (PCH) used as the transport channel. The PCH is a downlinktransport channel used to transport paging information to UEs. The PCHcan also be used to inform UEs about updates in the system information.In addition, the values (both fixed and variable) can be associated witha paging control channel (PCCH) used as the logic channel. The PCCH is adownlink logical channel which his used to notify UEs of a change in thesystem information.

FIG. 6 depicts a flow chart of a method 600 for enabling small datatransmissions in a user equipment (UE) configured for machine typecommunication (MTC) in accordance with an embodiment of the presentinvention. The method includes the operation of receiving 610, by the UEfrom an evolved node (eNB), a system information block (SIB). The SIBcan include information related to small data transmissions for MTC. Themethod 600 further comprises reading 620 system information included inthe SIB. The method 600 can further comprise performing 630 the smalldata transmission, from the UE to the eNB, based on the systeminformation included in the SIB.

The method 600 can also include the operations of reading a small datatransmission indicator in the system information included in the SIB andperforming the small data transmission by executing a fast radioresource connection (RRC), by the UE with the eNB, in response to thesmall data transmission indicator received from the eNB.

The method 600 can also include the operations of reading a small datatransmission command request in the system information included in theSIB and performing the small data transmission by sending uplinkmeasurement data, by the UE to the eNB, in response to the small datatransmission command request received from the eNB. In addition, themethod 600 can include the operation of reading a small data payload inthe SIB, received from the eNB at the UE, wherein the small data payloadis defined according to at least one of: a subscription; and a networkoperator policy.

In one embodiment, the operation of reading a small data payload in theSIB in the method 600 can include reading small data, at the UE, relatedto at least one of: a traffic congestion application; an energy wastageapplication; a home monitoring application; a parking guidanceapplication; and an electric meter reading application.

In one embodiment, the operation of executing the fast RRC connection inthe method 600 can include executing a RRC connection setup phase,without an establishment of bearers, between the UE and the eNB.

In one embodiment, the operation of performing the small datatransmission, from the UE to the eNB, based on the system informationincluded in the SIB, in the method 600 can include forming a connectionbetween the UE and the eNB after reading the SIB using a random accesschannel (RACH) and executing the fast RRC connection between the UE andthe eNB in order to perform the small data transmission. The method 600can also include entering an RRC idle mode by the UE after executing thefast RRC connection.

In one embodiment, the operation of receiving, by the UE from the eNB, aSIB, in the method 600 can include receiving, at the UE from the eNB, apaging notification indicating that the SIB includes system informationrelated to the UE, wherein the paging notification is received accordingto a paging cycle of the UE.

FIG. 7 illustrates an example user equipment (UE) 700 configured formachine type communication (MTC), as shown in another embodiment of thepresent invention. The UE comprises a multicast information transfermessage module 702 operable to receive a multicast information transfermessage, at the UE from an evolved node (eNB). The multicast informationtransfer message can notify the UE of updated system information in asystem information block (SIB) related to small data transmissions bythe UE. A SIB module 704 is configured to read the updated systeminformation in the SIB when notified of the change in the SIB by themulticast information transfer message from the eNB. The updated systeminformation in the SIB can relate to small data transmissionscommunicated by the UE. A small data transmission module 706 isconfigured to communicate the small data transmission to the eNB. Thesmall data transmission can be based on the updated system informationincluded as part of the multicast information transfer message.

In some embodiments, the multicast information transfer message module702 can be further configured to receive the multicast informationtransfer message from the eNB during a radio resource control (RRC) idlemode of the UE. In addition, the multicast information transfer messagemodule 702 can be further configured to receive the multicastinformation transfer message from the eNB in a paging cycle of the UEduring the RRC idle mode. In some embodiments of the present disclosure,the multicast information transfer message can include at least one of:a small data payload; a small data transmission indicator; and a smalldata command request.

In some embodiments, the multicast information transfer message module702 can be configured to read a small data payload in the multicastinformation transfer message. In addition, the multicast informationtransfer message module 702 can include monitoring a Physical DownlinkControl Channel (PDCCH) during the RRC idle mode of the UE andidentifying a Multicast Radio Network Temporary Identifier (MC-RNTI)indicating that the multicast information transfer message is receivedfrom the eNB.

In some embodiments, the SIB module 704 can be configured to read asmall data transmission indicator in the updated system information,wherein the updated system information is received by the UE in themulticast information transfer message. In addition, the SIB module 704can be configured to read a small data transmission command request inthe updated system information, wherein the updated system informationis received, by the UE in the multicast information transfer message.

In some embodiments, the small data transmission module 706 can beconfigured to perform the small data transmission by establishing aradio resource connection (RRC) with the eNB, in response to the smalldata transmission indicator received in the multicast informationtransfer message. In addition, the small data transmission module 706can be configured to perform the small data transmission by sendinguplink measurement data, by the UE to the eNB, in response to the smalldata transmission command request received as part of the multicastinformation transfer message.

In some embodiments of the present invention, the example user equipment(UE) 700 can be configured to communicate with an evolved node (eNB).The eNB may contain circuitry configured to receive a multicastinformation transfer message from a Mobility Management Entity (MME);determine a Multicast Radio Network Temporary Identifier (MC-RNTI) usedfor transmitting the multicast information transfer message to a userequipment (UE), wherein the MC-RNTI is one of a fixed value or avariable value that is derived at the eNB using an International MobileSubscriber Identity (IMSI) received from the MME; and transmit themulticast information transfer message, from the eNB to the UE, based onthe MC-RNTI of the UE.

In one embodiment, the multicast information transfer message caninclude at least one of a: a small data payload, a small datatransmission indicator, and a small data transmission command request.In addition, the small data payload can include at least one of: atraffic congestion application; an energy wastage application; a homemonitoring application; a parking guidance application; and an electricmeter reading application.

In some embodiments, the eNB may include circuitry configured totransmit the multicast information transfer message to at least one of:a specific UE, a single multicast group of UEs based on the fixedMC-RNTI, and a plurality of multicast groups of UEs based on thevariable MC-RNTI, wherein the MC-RNTI is used to identify selected UEswithin an Evolved Universal Mobile Telecommunications System TerrestrialRadio Access Network (E-UTRAN).

In some embodiments, the present disclosure can include at least onenon-transitory computer readable medium having instructions storedthereon for enabling small data transmissions in a user equipment (UE)configured for machine type communication (MTC), the instructions whenexecuted on a machine to cause the machine to: receive, by the UE froman evolved node (eNB), a system information block (SIB) including systeminformation related to small data transmissions for MTC; read, by theUE, the SIB including the system information related to the small datatransmissions; and perform the small data transmissions, from the UE tothe eNB, based on the system information read by the UE.

In one embodiment, the system information included in the computerreadable medium can include at least of: a small data transmissionindicator; a small data transmission command request; and a small datapayload.

In some embodiments, the computer readable medium can includeinstructions stored thereon for reading the SIB based on receiving amulticast information transfer message from the eNB during a radioresource control (RRC) idle mode of the UE, wherein the multicastinformation transfer message indicates that system information relatedto small data transmissions is included in the SIB.

FIG. 8 provides an example illustration of a mobile communicationdevice, such as a user equipment (UE), a mobile station (MS), a mobilewireless device, a tablet, a handset, or another type of mobile wirelessdevice. The mobile device can include one or more antennas configured tocommunicate with a base station (BS), an evolved Node B (eNB), or othertype of wireless wide area network (WWAN) access point. While twoantennas are shown, the mobile device may have between one and four ormore antennas. The mobile device can be configured to communicate usingat least one wireless communication standard including 3GPP LTE,Worldwide Interoperability for Microwave Access (WiMAX), High SpeedPacket Access (HSPA), Bluetooth, and WiFi. The mobile device cancommunicate using separate antennas for each wireless communicationstandard or shared antennas for multiple wireless communicationstandards. The mobile device can communicate in a wireless local areanetwork (WLAN), a wireless personal area network (WPAN), and/or awireless wide area network (WWAN).

FIG. 8 also provides an illustration of a microphone and one or morespeakers that can be used for audio input and output from the mobiledevice. The display screen may be a liquid crystal display (LCD) screen,or other type of display screen such as an organic light emitting diode(OLED) display. The display screen can be configured as a touch screen.The touch screen may use capacitive, resistive, or another type of touchscreen technology. An application processor and a graphics processor canbe coupled to internal memory to provide processing and displaycapabilities. A non-volatile memory port can also be used to providedata input/output options to a user. The non-volatile memory port mayalso be used to expand the memory capabilities of the mobile device. Akeyboard may be integrated with the mobile device or wirelesslyconnected to the mobile device to provide additional user input. Avirtual keyboard may also be provided using the touch screen.

It should be understood that many of the functional units described inthis specification have been labeled as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom VLSIcircuits or gate arrays, off-the-shelf semiconductors such as logicchips, transistors, or other discrete components. A module may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices or thelike.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of executable code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.The modules may be passive or active, including agents operable toperform desired functions.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, appearancesof the phrases “in one embodiment” or “in an embodiment” in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based ontheir presentation in a common group without indications to thecontrary. In addition, various embodiments and example of the presentinvention may be referred to herein along with alternatives for thevarious components thereof. It is understood that such embodiments,examples, and alternatives are not to be construed as defactoequivalents of one another, but are to be considered as separate andautonomous representations of the present invention.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, fasteners, sizes, lengths, widths, shapes, etc.,to provide a thorough understanding of embodiments of the invention. Oneskilled in the relevant art will recognize, however, that the inventioncan be practiced without one or more of the specific details, or withother methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring aspects of the invention.

While the forgoing examples are illustrative of the principles of thepresent invention in one or more particular applications, it will beapparent to those of ordinary skill in the art that numerousmodifications in form, usage and details of implementation can be madewithout the exercise of inventive faculty, and without departing fromthe principles and concepts of the invention. Accordingly, it is notintended that the invention be limited, except as by the claims setforth below.

What is claimed is:
 1. An apparatus of a user equipment (UE) operable toperform small data transmissions, the apparatus comprising: circuitryconfigured to: receive, from an eNodeB, a small data transmissionindicator that instructs the UE to establish a fast radio resourcecontrol (RRC) connection with the eNodeB; initiate, at the UE, a randomaccess channel (RACH) procedure in order to establish the fast RRCconnection with the eNodeB, wherein the fast RRC connection does notinclude the establishment of bearers between the UE and the eNodeB;receive a multicast information transfer message when in idle mode,wherein the UE is configured to periodically monitor a physical downlinkcontrol channel (PDCCH) to retrieve the multicast information transfermessage sent by the eNodeB; and perform, at the UE, a small datatransmission with the eNodeB using the fast RRC connection between theUE and the eNodeB; and a memory configured to communicate with thecircuitry and operable to store the multicast information transfermessage.
 2. The apparatus of the UE of claim 1, wherein the circuitry isconfigured to receive the small data transmission indicator from theeNodeB as part of a system information block (SIB).
 3. The apparatus ofthe UE of claim 1, wherein the circuitry is configured to receive thesmall data transmission indicator from the eNodeB as part of a multicastinformation transfer message.
 4. The apparatus of the UE of claim 1,wherein the circuitry is configured to receive the small datatransmission indicator from the eNodeB when the UE is in idle mode. 5.The apparatus of the UE of claim 1, wherein the circuitry is configuredto perform the small data transmission by sending a small data payloadto the eNodeB, wherein the small data payload is defined according to atleast one of: a subscription; and a network operator policy.
 6. Theapparatus of the UE of claim 1, wherein the circuitry is configured toperform the small data transmission by sending a small data payload tothe eNodeB, wherein the small data payload is related to at least oneof: a traffic congestion application; an energy wastage application; ahome monitoring application; a parking guidance application; or anelectric meter reading application.
 7. The apparatus of the UE of claim1, wherein the circuitry is configured to return back to idle mode afterperforming the small data transmission with the eNodeB using the fastRRC connection between the UE and the eNodeB.
 8. The apparatus of the UEof claim 1, wherein the circuitry is configured to establish the fastRRC connection with the eNodeB by performing an RRC connection setupcomplete phase, wherein the fast RRC connection does not include an RRCconnection reconfiguration message exchange for establishing bearersbetween the UE and the eNodeB.
 9. An apparatus of an eNodeB operable tofacilitate small data transmissions, the apparatus comprising: circuitryconfigured to: receive, from a mobility management entity (MME) amulticast information transfer message related to small datatransmissions; identify at least one set of idle user equipments (UEs)to receive the multicast information transfer message from the eNodeB,wherein each set of idle UEs are associated with a common MulticastRadio Network Temporary Identifier (MC-RNTI); and send the multicastinformation transfer message to the set of idle UEs, wherein the idleUEs are configured to periodically monitor a physical downlink controlchannel (PDCCH) to retrieve the multicast information transfer messagesent by the eNodeB; and a memory configured to communicate with thecircuitry and operable to store the multicast information transfermessage.
 10. The apparatus of the eNB of claim 9, wherein the circuitryis configured to send a small data transmission indicator to the set ofidle UEs as part of the multicast information transfer message, whereinthe small data transmission indicator instructs the idle UEs toestablish a fast radio resource control (RRC) connection with theeNodeB.
 11. The apparatus of the eNB of claim 9, wherein the circuitryis configured to send a small data transmission command request to theset of idle UEs as part of the multicast information transfer message,wherein the small data transmission command request instructs the idleUEs to send measurement data in uplink to the eNodeB, wherein the idleUEs are each configured to establish a fast radio resource control (RRC)connection with the eNodeB before sending the measurement data in uplinkvia the fast RRC connection.
 12. The apparatus of the eNB of claim 9,wherein the circuitry is configured to send a small data payload as partof the multicast information transfer message, wherein the small datapayload is related to at least one of: a traffic congestion application;an energy wastage application; a home monitoring application; a parkingguidance application; or an electric meter reading application.
 13. Theapparatus of the eNB of claim 9, wherein the circuitry is configured toreceive the multicast information transfer message from a machine typecommunication (MTC) server via the MME.
 14. At least one non-transitorymachine readable storage medium storing instructions which when executedby a processor perform the following: send a small data transmissionindicator to a machine type communication (MTC) device that instructsthe MTC device to establish a fast radio resource control (RRC)connection with the eNodeB; performing, a random access channel (RACH)procedure with the MTC device in order to establish the fast RRCconnection between the MTC device and the eNodeB, wherein the fast RRCconnection does not include the establishment of bearers between the MTCdevice and the eNodeB; receiving a multicast information transfermessage when in idle mode, wherein the UE is configured to periodicallymonitor a physical downlink control channel (PDCCH) to retrieve themulticast information transfer message sent by the eNodeB; andreceiving, a small data transmission from the MTC device using the fastRRC connection between the MTC device and the eNodeB.
 15. The at leastone non-transitory machine readable storage medium of claim 14, furthercomprising instructions while when executed by the at least one or moreprocessors performs the following: sending the small data transmissionindicator as part of a system information block (SIB).
 16. The at leastone non-transitory machine readable storage medium of claim 14, furthercomprising instructions while when executed by the at least one or moreprocessors performs the following: sending the small data transmissionindicator as part of a multicast information transfer message.
 17. Theat least one non-transitory machine readable storage medium of claim 14,further comprising instructions while when executed by the at least oneor more processors performs the following: sending the small datatransmission indicator when the MTC device is in idle mode.
 18. The atleast one non-transitory machine readable storage medium of claim 14,further comprising instructions while when executed by the at least oneor more processors performs the following: receiving the small datatransmission by receiving a small data payload from the MTC device,wherein the small data payload is defined according to at least one of:a subscription; and a network operator policy.
 19. The at least onenon-transitory machine readable storage medium of claim 14, furthercomprising instructions while when executed by the at least one or moreprocessors performs the following: receiving the small data transmissionby receiving a small data payload from the MTC device, wherein the smalldata payload is related to at least one of: a traffic congestionapplication; an energy wastage application; a home monitoringapplication; a parking guidance application; or an electric meterreading application.
 20. The at least one non-transitory machinereadable storage medium of claim 14, further comprising instructionswhile when executed by the at least one or more processors performs thefollowing: establishing the fast RRC connection with the MTC device byfacilitating an RRC connection setup complete phase, wherein the fastRRC connection does not include an RRC connection reconfigurationmessage exchange for establishing bearers between the MTC device and theeNodeB.